Shared control of camera device by multiple devices

ABSTRACT

Aspects of the present disclosure involve a system comprising a computer-readable storage medium storing at least one program, method, and user interface to facilitate a camera sharing session between two or more users. A camera sharing session is initiated based on session configuration information comprising a user identifier of a user permitted to control image capturing at a camera communicatively coupled to a first device. A trigger request is received from the second device and in response, an image capture, which results in at least one image, is triggered at the camera and the image is transmitted to the second device.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.16/443,614, filed Jun. 17, 2019, which is incorporated by referenceherein in its entirety.

TECHNICAL FIELD

The present disclosure generally relates to mobile and wearablecomputing technology. In particular, example embodiments of the presentdisclosure address systems, methods, and user interfaces to facilitateshared control of a camera device by multiple devices over a network.

BACKGROUND

Many wearable and mobile devices such as “smart” glasses include anembedded camera. Users of these devices often stream video produced byan embedded camera to other users' devices using mobile device softwareapplications and online platforms.

BRIEF DESCRIPTION OF THE DRAWINGS

To easily identify the discussion of any particular element or act, themost significant digit or digits in a reference number refer to thefigure number in which that element or act is first introduced.

FIG. 1 is a system diagram illustrating an example communication systemfor facilitating a camera sharing session between two or more users,according to some example embodiments.

FIG. 2 is a diagram illustrating a wearable companion device for use ina camera sharing session, according to some example embodiments.

FIG. 3 is a block diagram illustrating aspects of the wearable device,according to some example embodiments.

FIG. 4 is a schematic diagram illustrating data which may be stored in adatabase of a messaging server system, according to example embodiments.

FIG. 5 is a schematic diagram illustrating a structure of a messagegenerated by a messaging client application for communication, accordingto example embodiments.

FIGS. 6A-6H are conceptual diagrams illustrating a timeline of anexample camera sharing session between two users, according to someexample embodiments.

FIGS. 7-11 are flowcharts illustrating operations of the messagingsystem in performing a method for toggling between a conversation viewand a camera feed view, according to example embodiments.

FIG. 12 is a block diagram illustrating a representative softwarearchitecture, which may be used in conjunction with various hardwarearchitectures herein described, according to example embodiments.

FIG. 13 is a block diagram illustrating components of a machine able toread instructions from a machine-readable medium (e.g., amachine-readable storage medium) and perform any one or more of themethodologies discussed herein, according to example embodiments.

DETAILED DESCRIPTION Description

The description that follows includes systems, methods, techniques,instruction sequences, and computing machine program products thatembody illustrative embodiments of the disclosure. In the followingdescription, for the purposes of explanation, numerous specific detailsare set forth in order to provide an understanding of variousembodiments of the inventive subject matter. It will be evident,however, to those skilled in the art, that embodiments of the inventivesubject matter may be practiced without these specific details. Ingeneral, well-known instruction instances, protocols, structures, andtechniques are not necessarily shown in detail.

As noted above, users of mobile and wearable devices often stream videoproduced by an embedded camera to other users' devices using mobiledevice software applications and online platforms. With traditionalvideo streaming paradigms, a continuous video stream is provided by onedevice over a network to one or more other devices. However, traditionalvideo streaming paradigms are problematic for wearable and mobile deviceimplementations given the devices' hardware limitations. For example,these devices have limited space for circuitry and power and as aresult, the continuous streaming of the video drains device batteriesand heats up the devices' central processing unit (CPU), especially thatof the device providing the continuous video stream for an extendedduration. Moreover, the limited display screen space of wearable andmobile devices makes it challenging for users to meaningfullycommunicate and interact during a video streaming session. In addition,conventional video streaming applications and platforms typicallyrequire that a user's friends or followers be online to view contentfrom a video streaming session.

Aspects of the present disclosure address the foregoing issues byimproving upon traditional video streaming technology with systems,methods, techniques, instruction sequences, and computing machineprogram products for facilitating a camera sharing session between twoor more users. During a camera sharing session, single frame images orshort videos captured by a camera of a first user (e.g., an embeddedcamera of a mobile or wearable device) are sent to one or more otherusers' devices rather than provides those devices with a continuousstream of video content, as with traditional video streaming. Providingonly single frame images or short videos rather than a continuous streamof video content during a camera sharing session results in a reductionof device power consumption and computational processing resourceutilization compared to traditional video streaming.

Further, the second user can receive image data (single frame images orshort videos) sent by the first user during a camera sharing sessioneven if the second user is not online during the camera sharing session.Thus, camera sharing sessions, as set forth herein, further improve uponlimitations of traditional video streaming technology.

In addition, the second user can remotely (e.g., from a distance)control image capturing functionality at the camera of the first userduring the camera sharing session. Allowing the second user to controlthe camera of the first user during the camera sharing session increasesthe interactivity and engagement of users that is lacking in traditionalvideo streaming paradigms.

Consistent with some embodiments, a method may include initiating acamera sharing session based on session configuration information. Thesession configuration information comprises a user identifiercorresponding to a user permitted to control, during the camera sharingsession, image capturing at a camera communicatively coupled to a firstdevice. The initiating of the camera sharing session may comprisetransmitting, to a second device associated with the user, an invitationto join the camera sharing session. Based on an indication of the userjoining the camera sharing session, a first image capture may betriggered at the camera resulting in first image data comprising atleast a first image. A first message comprising the first image data istransmitted to the second device. A trigger request is received from thesecond device and in response, a second image capture is triggered atthe camera resulting in second image data comprising at least a secondimage. A second message comprising the second image data is transmittedto the second device.

Drawings

FIG. 1 is a system diagram illustrating an example communication system100 for facilitating a camera sharing session between two or more users,according to some example embodiments. The communication system 100 may,for example, be a messaging system where clients communicate andexchange data within the communication system 100, where certain data iscommunicated to and from wearable devices described herein. The data maypertain to various functions (e.g., sending and receiving image contentas well as text and other media communication) and aspects associatedwith the communication system 100 and its users. Although thecommunication system 100 is illustrated herein as having a client-serverarchitecture, other embodiments may include other network architectures,such as peer-to-peer or distributed network environments.

As shown in FIG. 1, the communication system 100 includes a messagingsystem 130. The messaging system 130 is generally based on athree-tiered architecture, consisting of an interface layer 124, anapplication logic layer 126, and a data layer 128. As is understood byskilled artisans in the relevant computer and Internet-related arts,each module or engine shown in FIG. 14 represents a set of executablesoftware instructions and the corresponding hardware (e.g., memory andprocessor) for executing the instructions. In various embodiments,additional functional modules and engines may be used with a messagingsystem, such as that illustrated in FIG. 1, to facilitate additionalfunctionality that is not specifically described herein. Furthermore,the various functional modules and engines depicted in FIG. 1 may resideon a single server computer or may be distributed across several servercomputers in various arrangements. Moreover, although the messagingsystem 130 is depicted in FIG. 1 as having a three-tiered architecture,the inventive subject matter is by no means limited to such anarchitecture.

As shown in FIG. 1, the interface layer 124 consists of interfacemodules (e.g., a web server) 140, which receive requests from variousclient-devices and servers, such as client devices 110-1 and 110-2executing client application 112. In response to received requests, theinterface modules 140 communicate appropriate responses to requestingdevices via a network 104. For example, the interface modules 140 canreceive requests such as Hypertext Transfer Protocol (HTTP) requests orother web-based application programming interface (API) requests.

The client devices 110 can execute conventional web browser applicationsor applications (also referred to as “apps”) that have been developedfor a specific platform to include any of a wide variety of mobiledevices and mobile-specific operating systems (e.g., IOS™, ANDROID™,WINDOWS® PHONE). In an example, the client devices 110 are executing theclient application 112. The client application 112 can providefunctionality to present information to users 106-1 and 106-2 andcommunicate via the network 104 to exchange information with themessaging system 130. Each of the client devices 110-1 and 110-2 cancomprise a device that includes at least a display and communicationcapabilities with the network 104 to access the messaging system 130.The client devices 110 comprise, but are not limited to, remote devices,work stations, computers, general-purpose computers, Internetappliances, hand-held devices, wireless devices, portable devices,wearable computers, cellular or mobile phones, personal digitalassistants (PDAs), smart phones, tablets, ultrabooks, netbooks, laptops,desktops, multi-processor systems, microprocessor-based or programmableconsumer electronics, game consoles, set-top boxes, network personalcomputers (PCs), mini-computers, and the like. The users 106-1 and 106-2can include a person, a machine, or other means of interacting with theclient devices 110. In some embodiments, the users 106-1 and 106-2interact with the messaging system 130 via the client devices 110-1 and110-2, respectively.

As shown, the communication system 100 additionally includes a companiondevice 114 communicatively connected to the client device 110-1. Invarious embodiments, the companion device 114 is configured for wiredcommunication with either the client device 110-1 or the messagingsystem 130. The companion device 114 may also be simultaneouslyconfigured for wireless communication with the client device 110-1, themessaging system 130, or both. The companion device 114 may be awearable device such as glasses, a visor, a watch, or othernetwork-enabled items. The companion device 114 may also be any devicedescribed herein that accesses a network such as network via anotherdevice such as the client device 110-1.

The companion device 114 include image sensors 116 and wireless inputand output (I/O) 118. The companion device 114 may include one or moreprocessors, a display, a battery, and a memory, but may have limitedprocessing and memory resources. In such embodiments, the client device110-1 and/or server devices used for the messaging system 130 may beused via network connections to provide remote processing and memoryresources for the companion devices 114. In one embodiment, for example,the client companion device 114 may be a pair of network-enabledglasses, such as glasses 231 of FIG. 2, and the client device 110-1 maybe a smartphone that enables access to the messaging system 130 toenable communication of image content captured with the image sensor(s)116.

As shown in FIG. 1, the data layer 128 has one or more database servers132 that facilitate access to information storage repositories ordatabases 134. The databases 134 are storage devices that store datasuch as member profile data, social graph data (e.g., relationshipsbetween members of the messaging system 130), and other user data.

An individual can register with the messaging system 130 to become amember of the messaging system 130. Once registered, a member can formsocial network relationships (e.g., friends, followers, or contacts) onthe messaging system 130 and interact with a broad range of applicationsprovided by the messaging system 130.

The application logic layer 126 includes various application logicmodules 150, which, in conjunction with the interface modules 140,generate various user interfaces with data retrieved from various datasources or data services in the data layer 128. Individual applicationlogic modules 150 may be used to implement the functionality associatedwith various applications, services, and features of the messagingsystem 130. For instance, a messaging application can be implementedwith one or more of the application logic modules 150. The messagingapplication provides a messaging mechanism for users of the clientdevices 110-1 and 110-2 to send and receive messages that include textand media content such as pictures and video. The client devices 110-1and 110-2 may access and view the messages from the messagingapplication for a specified period of time (e.g., limited or unlimited).In an example, a particular message is accessible to a message recipientfor a predefined duration (e.g., specified by a message sender) thatbegins when the particular message is first accessed. After thepredefined duration elapses, the message is deleted and is no longeraccessible to the message recipient.

Additionally, the application logic modules 150 embodying the messagingapplication or other application logic modules 150 may providefunctionality to facilitate a camera sharing session between the users106-1 and 106-2. Within the context of a camera sharing session, theuser 106-2 may control a camera 160 of the user 106-1. Morespecifically, the user 106-2 may utilize the client application 112executing on the client device 110-2 to trigger image capturing at thecamera 160. At each instance where the user 106-2 triggers an imagecapture at the camera 106, image data is generated and a messagecomprising the image data is transmitted to the client device 106-2. Themessage may further include audio data recorded in conjunction with thecapturing of the image data. The image data may comprise as single imageframe or a short video (e.g., comprising multiple image frames). Byproviding single frame images or short videos to the client device 106-2during the camera sharing session, rather than a continuous stream ofvideo content as done in traditional video streaming, the messagingsystem 130 reduces power consumption and use of computational processingresources at both the client devices 106-1 and 106-2, at least comparedto traditional video streaming.

The camera 160 is communicatively coupled to the client device 110-1.For example, in some embodiments, the camera 160 may be embedded in theclient device 110-1 (e.g., a smartphone with an embedded camera). Insome embodiments, the camera 160 may be embedded in the companion device114 and may comprise or correspond to the image sensor(s) 116.

FIG. 2 is a diagram illustrating a wearable companion device 114 in theexample form of glasses 231 for use in a camera sharing session,according to some example embodiments. The glasses 231 can include aframe 232 made from any suitable material such as plastic or metal,including any suitable shape memory alloy. The frame 232 can have afront piece 233 that can include a first or left lens, display, oroptical element holder 236 and a second or right lens, display, oroptical element holder 237 connected by a bridge 238. The front piece233 additionally includes a left end portion 241 and a right end portion242. A first or left optical element 244 and a second or right opticalelement 243 can be provided within respective left and right opticalelement holders 236, 237. Each of the optical elements 243, 244 can be alens, a display, a display assembly, or a combination of the foregoing.In some embodiments, for example, the glasses 231 are provided with anintegrated near-eye display mechanism that enables, for example, displayto the user of preview images for visual media captured by cameras 269of the glasses 231.

The frame 232 additionally includes a left arm or temple piece 246 and aright arm or temple piece 247 coupled to the respective left and rightend portions 241, 242 of the front piece 233 by any suitable means, suchas a hinge (not shown), so as to be coupled to the front piece 233, orrigidly or fixably secured to the front piece 233 so as to be integralwith the front piece 33. Each of the temple pieces 246 and 247 caninclude a first portion 251 that is coupled to the respective endportion 241 or 242 of the front piece 233 and any suitable secondportion 252, such as a curved or arcuate piece, for coupling to the earof the user. In one embodiment, the front piece 233 can be formed from asingle piece of material, so as to have a unitary or integralconstruction. In one embodiment, the entire frame can be formed from asingle piece of material so as to have a unitary or integralconstruction.

The glasses 231 can include a device, such as a computer 261, which canbe of any suitable type so as to be carried by the frame 232 and, in oneembodiment, of a suitable size and shape so as to be at least partiallydisposed in one of the temple pieces 246 and 247. In one embodiment, thecomputer 261 has a size and shape similar to the size and shape of oneof the temple pieces 246, 247 and is thus disposed almost entirely ifnot entirely within the structure and confines of such temple pieces 246and 247. In one embodiment, the computer 261 can be disposed in both ofthe temple pieces 246, 247. The computer 261 can include one or moreprocessors with memory, wireless communication circuitry, and a powersource. The computer 261 comprises low-power circuitry, high-speedcircuitry, and a display processor. Various other embodiments mayinclude these elements in different configurations or integratedtogether in different ways.

The computer 261 additionally includes a battery 262 or other suitableportable power supply. In one embodiment, the battery 262 is disposed inone of the temple pieces 246 or 247. In the glasses 231 shown in FIG. 2,the battery 262 is shown as being disposed in the left temple piece 246and electrically coupled using a connection 274 to the remainder of thecomputer 261 disposed in the right temple piece 247. One or more I/Odevices can include a connector or port (not shown) suitable forcharging a battery 262 accessible from the outside of the frame 232, awireless receiver, transmitter, or transceiver (not shown), or acombination of such devices. Given the limited size of the glasses 231and the computer 261, resource intensive operations such as videostreaming can quickly drain the battery 262 and can be a strain on theone or more processors of the computer 261 that can lead to overheating.

The glasses 231 include digital cameras 269. Although two cameras 269are depicted, other embodiments contemplate the use of a single oradditional (i.e., more than two) cameras. For ease of description,various features relating to the cameras 269 will further be describedwith reference to only a single camera 269, but it will be appreciatedthat these features can apply, in suitable embodiments, to both cameras269.

Consistent with some embodiments, the cameras 269 are examples of thecamera 160 of the first user 106-1 discussed above in reference toFIG. 1. Accordingly, in these embodiments, the glasses 231 may be wornby the user 106-1. Further, in these embodiments, the user 106-2 may beenabled to control image capture by the cameras 269 as part of a camerasharing session. During the camera sharing session, single frame imagesor short videos generated by the cameras 269 are sent to the clientdevice 110-2. By providing only single frame images or short videos tothe client device 106-2 during the camera sharing session, rather than acontinuous stream of video content as is done in traditional videostreaming, power consumption from the battery 262 and the strain on theone or more processors of the computer 261 is reduced compared at leastto traditional video streaming.

In various embodiments, the glasses 231 may include any number of inputsensors or peripheral devices in addition to the cameras 269. The frontpiece 233 is provided with an outward-facing, forward-facing, front, orouter surface 266 that faces forward or away from the user when theglasses 231 are mounted on the face of the user, and an oppositeinward-facing, rearward-facing, rear, or inner surface 267 that facesthe face of the user (e.g., user 106-1) when the glasses 231 are mountedon the face of the user. Such sensors can include inward-facing videosensors or digital imaging modules such as cameras that can be mountedon or provided within the inner surface 267 of the front piece 233 orelsewhere on the frame 232 so as to be facing the user, andoutward-facing video sensors or digital imaging modules such as thecameras 269 that can be mounted on or provided with the outer surface266 of the front piece 233 or elsewhere on the frame 232 so as to befacing away from the user. Such sensors, peripheral devices, orperipherals can additionally include biometric sensors, locationsensors, accelerometers, or any other such sensors.

The glasses 231 further include an example embodiment of a cameracontrol mechanism or user input mechanism comprising a camera controlbutton mounted on the frame 232 for haptic or manual engagement by theuser. The camera control button provides a bi-modal or single-actionmechanism in that it is disposable by the user between only twoconditions, namely an engaged condition and a disengaged condition. Inthis example embodiment, the camera control button is a pushbutton thatis by default in the disengaged condition, being depressible by the userto dispose it to the engaged condition. Upon release of the depressedcamera control button, it automatically returns to the disengagedcondition.

In other embodiments, the single-action input mechanism can instead beprovided by, for example, a touch-sensitive button comprising acapacitive sensor mounted on the frame 232 adjacent to its surface fordetecting the presence of a user's finger to dispose the touch-sensitivebutton to the engaged condition when the user touches a finger to thecorresponding spot on the outer surface of the frame 232. It will beappreciated that the above-described camera control button andcapacitive touch button are but two examples of a haptic input mechanismfor single-action control of the camera 269 and that other embodimentsmay employ different single-action haptic control arrangements.

FIG. 3 is a block diagram illustrating aspects of the wearable device inthe example form of the glasses 231, according to some exampleembodiments. The computer 261 of the glasses 231 includes a centralprocessor 321 in communication with an onboard memory 326. The centralprocessor 321 may be a CPU and/or a graphics processing unit (GPU). Thememory 326 in this example embodiment comprises a combination of flashmemory and random-access memory.

The glasses 231 further include a camera controller 314 in communicationwith the central processor 321 and the camera 269. The camera controller314 comprises circuitry configured to control recording of eitherphotographic content or video content based upon processing of controlsignals received from the single-action input mechanism that includesthe camera control button, and to provide for automatic adjustment ofone or more image-capture parameters pertaining to capturing of imagedata by the camera 269 and on-board processing of the image data priorto persistent storage thereof and/or to presentation thereof to the userfor viewing or previewing.

In some embodiments, the camera controller 314 comprises permanentlyconfigured circuitry, such as firmware or an application-specificintegrated circuit (ASIC) configured to perform the various functionsdescribed herein. In other embodiments, the camera controller 314 maycomprise a dynamically reconfigurable processor executing instructionsthat temporarily configure the processor to execute the variousfunctions described herein.

The camera controller 314 interacts with the memory 326 to store,organize, and present image content in the form of photo content andvideo content. To this end, the memory 326 in this example embodimentcomprises a photo content memory 328 and a video content memory 342. Thecamera controller 314 is thus, in cooperation with the central processor321, configured to receive from the camera 269 image data representativeof digital images produced by the camera 269 in accordance with some ofthe image-capture parameters, to process the image data in accordancewith some of the image-capture parameters, and to store the processedimage data in an appropriate one of the photo content memory 328 and thevideo content memory 342.

The camera controller 314 is further configured to cooperate with adisplay controller 349 to cause display on a display mechanismincorporated in the glasses 231 of selected photos and videos in thememory 326 and thus to provide previews of captured photos and videos.In some embodiments, the camera controller 314 will manage processing ofimages captured using automatic bracketing parameters for inclusion in avideo file.

A single-action input mechanism 335 is communicatively coupled to thecentral processor 321 and the camera controller 314 to communicatesignals representative of a current state of the camera control buttonand thereby to communicate to the camera controller 314 whether or notthe camera control button is currently being pressed. The cameracontroller 314 further communicates with the central processor 321regarding the input signals received from the single-action inputmechanism 335. In one embodiment, the camera controller 314 isconfigured to process input signals received via the single-action inputmechanism 335 to determine whether a particular user engagement with thecamera control button is to result in a recording of video content orphotographic content and/or to dynamically adjust one or moreimage-capture parameters based on processing of the input signals. Forexample, pressing of the camera control button for longer than apredefined threshold duration causes the camera controller 314automatically to apply relatively less rigorous video processing tocaptured video content prior to persistent storage and display thereof.Conversely, pressing of the camera control button for shorter than thethreshold duration in such an embodiment causes the camera controller314 automatically to apply relatively more rigorous photo stabilizationprocessing to image data representative of one or more still images.

The glasses 231 may further include various components common to mobileelectronic devices such as smart glasses or smart phones (for example,including a display controller for controlling display of visual media(including photographic and video content captured by the camera 269) ona display mechanism incorporated in the device). Note that the schematicdiagram of FIG. 3 is not an exhaustive representation of all componentsforming part of the glasses 231.

FIG. 4 is a schematic diagram illustrating data 400 which may be storedin one or more of the databases 134 of the messaging system 130,according to certain example embodiments. While the content of the data400 is shown to comprise a number of tables, it will be appreciated thatthe data 400 could be stored in other types of data structures (e.g., asan object-oriented database).

The data 400 includes message data stored within a message table 402. Anentity table 404 stores entity data, including an entity graph 406.Entities for which records are maintained within the entity table 404may include individuals, corporate entities, organizations, objects,places, events, and so forth. Regardless of type, any entity regardingwhich the messaging server system 108 stores data may be a recognizedentity. Each entity is provided with a unique identifier, as well as anentity type identifier (not shown).

The entity graph 406 furthermore stores information regardingrelationships and associations between entities. Such relationships maybe social, professional (e.g., work at a common corporation ororganization), interested-based, or activity-based, merely for example.

A video table 408 stores video data associated with messages for whichrecords are maintained within the message table 402. Similarly, an imagetable 410 stores image data associated with messages for which messagedata is stored in the message table 402.

A conversation table 412 stores data regarding chat conversations andassociated content (e.g., image, video, or audio data). A record foreach chat conversation may be maintained in the conversation table 412.Each record may include a unique identifier for the chat conversation, aretention duration attribute, identifiers of entities that areparticipants in the chat conversation (or pointers to the identifiers inthe entity table 404), and message data (or pointers to correspondingmessage data in the message table 402).

FIG. 5 is a schematic diagram illustrating a structure of a message 500,according to some embodiments, generated by a client application 112 forcommunication to a further client application 112 or one or moreapplication logic modules 150. The content of a particular message 500is used to populate the message table 402 stored within database 134,accessible by the application logic modules 150. Similarly, the contentof a message 500 is stored in memory as “in-transit” or “in-flight” dataof one of the client devices 110-1 or 110-2 or the messaging system 130.The message 500 is shown to include the following components:

-   -   A message identifier 502: a unique identifier that identifies        the message 500.    -   A message text payload 504: text, to be generated by a user via        a user interface of one of the client devices 110-1 or 110-2 and        that is included in the message 400.    -   A message image payload 506: image data, captured by a camera        component of one of the client devices 110-1 or 110-2 or        retrieved from memory of one of the client devices 110-1 or        110-2, and that is included in the message 500.    -   A message video payload 508: video data, captured by a camera        component or retrieved from a memory component of one of the        client device 110-1 or 110-2 and that is included in the message        500.    -   A message audio payload 510: audio data, captured by a        microphone or retrieved from the memory component of one of the        client device 110-1 or 110-2, and that is included in the        message 500.    -   A message duration attribute 512: an attribute value indicating,        in seconds, the amount of time for which content of the message        500 (e.g., the message image payload 506, message video payload        508, and message audio payload 510) is to be made accessible to        a user via the client application 112 upon accessing the message        500.    -   A conversation identifier 514: an identifier indicative of the        chat conversation to which the message belongs.    -   A message sender identifier 516: an identifier (e.g., a        messaging system identifier, email address, or device        identifier) indicative of a user of one of the client devices        110-1 or 110-2 on which the message 400 was generated and from        which the message 400 was sent.    -   A message receiver identifier 518: an identifier (e.g., a        messaging system identifier, email address, or device        identifier) indicative of a user of one of the client devices        110-1 and 110-2 to which the message 500 is addressed.

The contents (e.g., values) of the various components of the message 500may be pointers to locations in tables within which content data valuesare stored. For example, an image value in the message image payload 506may be a pointer to (or address of) a location within the image table410. Similarly, values within the message video payload 508 may point todata stored within the video table 408, values stored within theconversation identifier 514 may point to data stored within theconversation table 412, and values stored within the message senderidentifier 516 and the message receiver identifier 4518 may point touser records stored within the entity table 404.

FIG. 6A-6H are conceptual diagrams illustrating a timeline 600 of anexample camera sharing session between the user 106-1 (also referred toherein and in FIGS. 6A-6H as the “first user”) and at least the user106-2 (also referred to herein and in FIGS. 6A-6H as the “second user”),according to some example embodiments. In the context of the examplecamera sharing session described below, the second user is enabled tocontrol image capturing at the camera 160 of the first user. However, itshall be appreciated that the second user may be one of a plurality ofusers that are enabled to control image capturing at the camera 160 ofthe first users.

In some embodiments, the camera 160 of the first user is an embeddedcamera of the client device 110-1 such as a smartphone. In someembodiments, the camera 160 of the first user is an embedded camera ofthe companion device 114 such as a wearable device (e.g., glasses 231).

Consistent with these embodiments, the second user may utilize theclient application 112 executing on the client device 110-2 to controlthe image capturing at the camera 160 of the first user. In this examplecamera sharing session, the client application 112 is not initiallyexecuting on the client device 110-2 of the second user.

As shown in FIG. 6A, the example camera sharing session starts at T1. Atthe start of the camera sharing session the messaging system 130 sends afirst message to the client device 110-2 of the second user. The firstmessage comprises an invitation comprising first image data (e.g.,comprising at least a first image) captured by the camera 160 of thefirst user. The first message may further include audio datasimultaneously recorded by a microphone of the client device 110-1. Theinvitation is sent to the client device 110-2 of the second user basedon an inclusion of a user identifier of the second user being includedin session configuration information associated with the camera sharingsession. The session configuration information may be specified by thefirst user using the client application 112 executing on the clientdevice 110-1. The invitation may further include a textual descriptiongenerated by the first user that is included in the sessionconfiguration information.

As shown in FIG. 6B, at T2, the first user creates a second messagecomprising second image data (e.g., comprising at least a second image)generated by the camera 160 of the first user after the invitation issent to the client device 110-2 of the second user. As an example, insome embodiments, the second image data may be generated by a camera 269of the glasses 231 in response to a single press of the camera controlbutton mounted on the frame 232 by the first user. Within the secondmessage, the second image data may be augmented with additional contentsuch as text, emojis, graphics and other visual effects specified by thefirst user or added by default. The second message may further includeaudio data simultaneously recorded by the microphone of the clientdevice 110-1. The messaging system 130 sends the second message to theclient device 110-2 and causes the client device 110-2 to present anotification of the second message. Allowing the first user to generateand transmit image data with a single button press, as set forth above,provides a mechanism for sending images that increases the efficiency ofthe interaction compared to traditional user interface-basedmethodologies that may require the first user to navigate betweenmultiple windows or screens and perform potentially multiple buttonpresses. For example, traditional user interfaces require users to firstprovide input to capture image data (e.g., a single image frame orvideo), provide another input or series of inputs to choose recipientsfor the image data, and possibly another input to confirm/initiate thetransmission of that photo or video to the selected recipients.

As shown in FIG. 6C, upon the second user opening the client application112 on the client device 110-2, the client device 110-2 presents thefirst and second message to the second user, at T3. Upon viewing theinvitation, the second user may be provided an option to join the camerasharing session, and as shown in FIG. 6D, upon receiving an indicationof the second user joining the camera sharing session, the messagingsystem 130 triggers an image capture at the camera 160, which results ingeneration of third image data (e.g., comprising at least a thirdimage), at T4. In embodiments in which the image data includes a shortvideo, the messaging system 130 may initiate a video capture at thecamera that ends after a predefined period of time. The messaging system130 transmits a third message comprising at least the third image datato the client device 110-2 of the second user.

In embodiments in which the third image data includes a short video, inpresenting the third image data, the client device 110-2 may alsopresent an additional video feed depicting the first user in thesurrounding environment. Consistent with these embodiments, the clientdevice 110-1 or another display device in communication with the clientdevice 110-1 may simultaneously present a video feed depicting thesecond user. In this way, the messaging system 130 may allow the firstand second users to communicate directly with one another while alsoallowing the second user to share in the first user's experience. As anexample of the forgoing, suppose the first user is in an elephant safaripark in Thailand and is about to feed an elephant. In this example, thesecond user may want to experience the exact moment when the first userputs their hands near the elephant's mouth by viewing both the actualinteraction with the elephant as well as the first user's reaction tothe interaction.

As shown in FIG. 6E, at T5, the second user may trigger an additionalimage capture at the camera 160 by submitting a first trigger request tothe messaging system 130. The second user may submit the first triggerrequest via a GUI provided by an application running on the clientdevice 110-2. In response to the trigger request, the messaging system130 again triggers an image capture at the camera 160, thereby resultingin generation of fourth image data (e.g., comprising at least a fourthimage). The messaging system 130 transmits a fourth message to theclient device 110-2 that includes at least the fourth image data and mayfurther include audio data. As with the prior image capture, the firstuser may be provided with the option to prevent the image capture.

In some embodiments, prior to the image capture, the first user may beprovided the option to prevent the image capture. For example, in someembodiments, if the first user does not request to prevent the imagecapture after a specified period of time, the image capture will betriggered. In some embodiments, the first user may be required to permitthe image capture before it is triggered. As an example, in someembodiments, the first user may use a physical button of the glasses 231(e.g., the camera control button) to provide input indicative of eitherauthorization of the image capture or a request to prevent the imagecapture.

As shown in FIG. 6F, at T6, the messaging system 130 pauses the camerasharing session. The messaging system 130 may pause the camera sharingsession in response to input provided by the first user (e.g., at clientdevice 110-1 or at the companion device 114). Also at T6, the seconduser uses the client device 110-2 to submit a second trigger request tothe messaging system 130 while the camera sharing session is paused.Because the camera sharing session is paused, the messaging system 130adds the second trigger request to a request queue. The request queueincludes one or more trigger requests to be execution once the camerasharing session resumes.

As shown in FIG. 6G, the camera sharing session is resumed at T7, atwhich time the messaging system 130 executes the second trigger requestfrom the request queue, which results in generation of fifth image data(e.g., comprising at least a fifth image) by the camera 160. Themessaging system 130 transmits a fifth message to the client device110-2 of the second user that comprises at least the fifth image data.

As shown in FIG. 6H, at T8, the first user creates a sixth messagecomprising at least a sixth image generated by the camera 160. The sixthmessage is sent to the client device 110-2 of the second user and thecamera sharing session ends thereafter.

FIGS. 7-10 are flowcharts illustrating operations of the messagingsystem in performing a method 700 for facilitating a camera sharingsession between two or more users, according to example embodiments. Themethod 700 may be embodied in computer-readable instructions forexecution by one or more processors such that the operations of themethod 700 may be performed in part or in whole by the functionalcomponents of the communication system 100; accordingly, the method 700is described below by way of example with reference thereto. However, itshall be appreciated that at least some of the operations of the method700 may be deployed on various other hardware configurations than thecommunication system 700.

At operation 705, the messaging system 130 receives sessionconfiguration information from a first device (e.g., the client device110-1). The session configuration is specified by a user of the firstdevice (e.g., the user 106-1; hereinafter “first user”). The sessionconfiguration information comprises one or more identifierscorresponding to one or more users (e.g., the user 106-2) who arepermitted to control image capturing at a camera (e.g., the camera 160)that is communicatively coupled to the first device during a camerasharing session. For example, the session configuration informationincludes at least one user identifier corresponding to a second user(e.g., the user 106-2) who is permitted to control image capturing at acamera (e.g., the camera 160). The session configuration information mayfurther include a user-generated textual description associated with thecamera sharing session.

In some embodiments, the camera is an embedded camera of the firstdevice (e.g., a smartphone camera). In some embodiments, the camera isan embedded camera of a companion device (e.g., companion device 114)such as a wearable device (e.g., glasses 231).

Consistent with some embodiments, a messaging application (e.g., theclient application 112) executing on the first device may provide agraphical user interface (GUI) to the first device for inputting thesession configuration information. The GUI may include at least a firstinput field for specifying one or more user identifiers and a secondinput field for inputting a textual description associated with thecamera sharing session. Consistent with these embodiments, the firstuser may input the session configuration information using the GUI.

At operation 710, the communication system 100 initiates the camerasharing session based on the session configuration information. Theinitiating of the camera sharing session includes at least transmittingan invitation to a second device (e.g., the client device 110-2)associated with the second user included in the session configurationinformation. The communication system 100 may transmit an invitation toeach user specified in the session configuration information. Furtherdetails regarding the initiating of the camera sharing session arediscussed below in reference to FIG. 8, according to some exampleembodiments.

At operation 715, the messaging system 130 receives an indication fromthe second device (e.g., from the messaging application) of the seconduser joining the camera sharing and based on receiving the indication,the messaging system 100, at operation 720, triggers a first imagecapture at the camera. The first image capture results in generation offirst image data comprising at least a first image. The first image datamay include a single image from or a short video (e.g., 5 seconds)comprising multiple image frames. The messaging system 130 may triggeran image capture at the camera by transmitting a command to either thefirst device or a companion device that causes an image to be capturedby the camera. In embodiments in which the camera is embedded in acompanion device, the communication system 100 may either communicatethe command directly to the companion device or may communicate thecommand to the first device, which in turn transmits the command to thecompanion device to trigger the image capture.

At operation 725, the messaging system 130 transmits a first message tothe second device based on the first image capture. The first messagecomprises at least the first image data. In some embodiments, the firstmessage may comprise the first image data augmented with additionalcontent (e.g., text, emojis, graphics, and/or visual effects). The firstimage data may be augmented with the additional content based on userinput. The first message may further include audio data simultaneouslyrecorded with the capturing of the first image data.

At operation 730, the messaging system 130 receives a trigger requestfrom the second device. Consistent with some embodiments, a messagingapplication (e.g., the client application 112) executing on the seconddevice may provide a GUI that includes functionality to enable thesecond user to submit the trigger request. For example, the GUI mayinclude a button or other selectable element, the selection of whichinvokes a trigger request.

At operation 735, the messaging system 130 triggers a second imagecapture at the camera based on receiving the trigger request. The secondimage capture results in generation of second image data comprising atleast a second image. As with the first image data, the second imagedata may include a single image from or a short video (e.g., 5 seconds)comprising multiple image frames. In this way, the camera sharingsession allows the second user to remotely trigger image capturing atthe camera of the first user. As noted above, the messaging system 130may trigger the second image capture by transmitting a command to thefirst device or the companion device, depending on the embodiment. Inembodiments in which the image data includes a short video, themessaging system 130 may initiate a video capture at the camera thatends after a predefined period of time (e.g., 5 seconds).

At operation 740, the messaging system 130 transmits a second message tothe second device based on the second image capture. The second messagecomprises at least the second image data.

In the context of the method 700 described above, a single image framesor short videos (e.g., 5 seconds) are sent to the second device duringthe camera sharing session. That is, rather than providing a continuousvideo stream to allow the first user to share his or her experience withthe second user, the method 700 allows the first user's experience to beshared with the second user in single frame image or short videoincrements. Providing only single frame images or short videos ratherthan a continuous stream of video content results in a reduction ofdevice power consumption and computational processing resourceutilization compared to traditional video streaming while still allowingthe first user to share an experience with the second user via imagecontent at any time or location, as if the second user were watchinglive.

As shown in FIG. 8, the method 700 may further include operations 805,810, 815, 820, and 825, in some embodiments. Consistent with theseembodiments, the operations 805, 810, and 815 may be performed as partof operation 710 where the communication system 100 initiates the camerasharing session. At operation 805, the messaging system 130 activatesthe camera of the first user, which causes the camera to start producingimage data. The image data includes images that depict a real-worldscene that is within a field of view of the camera. As noted below inreference to FIG. 10, the second user may, in some embodiments, beenabled to control the field of view of the camera as well.

At operation 810, the messaging system 130 triggers a third imagecapture at the camera. The third image capture results in generation ofthird image data (e.g., comprising at least a third image). At operation815, the messaging system 130 transmits an invitation to the seconddevice inviting the second user to join the camera sharing session. Theinvitation includes at least the third image data and may furtherinclude the user-generated textual description associated with thecamera sharing session. In some instances, the second user may beinactive when the camera sharing session begins (e.g., if the seconduser is offline or the messaging application is not executing on thefirst device). In these instances, the invitation may be added to aqueue of unread messages stored by the second device that may be viewedby the second user when the second user opens the messaging application,or the invitation may simply be transmitted to the second device uponthe second user opening the messaging application. In instances in whichthe invitation is added to the queue, the messaging system 130 may, insome instances, cause a notification (e.g., a push notification) to bepresented by the second device.

Consistent with these embodiments, the operations 820 and 825 may beperformed subsequent to the operation 710, where the communicationsystem 100 initiates the camera sharing session. At operation 820, themessaging system 130 captures fourth image data (e.g., comprising atleast a fourth image) generated by the camera. The capturing of thefourth image data may be in response to user input of the first userreceived at the first device or a companion device. For example, in someembodiments, the capturing of the fourth image data may be in responseto the first user pressing the camera control button of the glasses 231.

At operation 825, the communication system 100 transmits a fourthmessage to the second device. The fourth message may be automaticallytransmitted based on the user input that triggered the capturing of thefourth image data, consistent with some embodiments. The fourth messagecomprises at least the fourth message data and may further include audiodata, for example. As with the invitation, in instances in which thesecond user is not online, the fourth message may be added to a queue ofunread messages stored by the second device that may be viewed by thesecond user when the second user opens the messaging application on thesecond device, or the fourth message may simply be transmitted to thesecond device upon the second user opening the messaging application onthe second device.

As shown in FIG. 9, the method 700 may, in some embodiments, includeoperations 905, 910, 915, and 920. Consistent with these embodiments,the operations 905 and 910 may be performed prior to operation 720,where the messaging system 130 triggers the first image capture at thecamera. At operation 905, the messaging system 130 provides a firstnotification to the first device. The first notification notifies thefirst user of the imminence of the first image capture. The firstnotification may, for example, comprise a graphical notificationpresented by the first device or a companion device, or may comprise amore simplistic notification such as an audio notification (e.g., anoise or ringer), a haptic notification (e.g., a vibration), or a visualnotification (e.g., a light blink) provided by the first device, thecompanion device, or both.

In some embodiments, trigger requests may be accepted by default and thefirst user may be provided with the option to prevent the first imagecapture. Consistent with these embodiments, the first image capture mayoccur after a predefined amount of time if the first user has notprovided input to indicate that the first image capture is to beprevented.

In some embodiments, trigger requests may be rejected by default and thefirst user may be provided with an ability to permit the first imagecapture. Consistent with these embodiments, the first image capture maynot occur unless the first user provides authorization within apredefined amount of time.

In some embodiments, the first user may be provided with the option toeither permit the image capture or prevent the image capture. Dependingon the embodiment, the first user may provide input to the first deviceor a companion device to either permit or prevent the first imagecapture. For example, in some embodiments, the first user may utilize abutton mounted on the glasses 231 (e.g., the camera control button) toindicate whether the camera sharing session is to be permitted orprevented.

At operation 910, the messaging system 130 detects authorization of thefirst image capture. In some embodiments, the detecting of theauthorization may include determining that the specified amount of timeexpired without the first user providing input to indicate that thefirst image capture is to be prevented. In some embodiments, thedetecting of the authorization may include receiving input indicative ofthe first user permitting the first image capture. In a first example,the messaging system 130 receives selection of a button or otherselectable element presented within a GUI displayed on the first devicethat indicates that the first image capture is to be permitted. In asecond example, the communication system 100 detects a button press onthe companion device of the first device that indicates that the firstimage capture is to be permitted (e.g., a press of a button mounted onthe glasses 231).

Consistent with these embodiments, the operations 915 and 920 may beperformed prior to operation 735 where the messaging system 130 triggersthe second image capture. At operation 915, the messaging system 130provides a second notification to the first device. The secondnotification notifies the first user of the imminence of the secondimage capture. As with the first notification, the second notificationmay provide the first user the ability to permit the second imagecapture or to prevent the second image capture. Likewise, the secondnotification may, for example, comprise a graphical notificationpresented by the first device or a companion device, or may comprise amore simplistic notification such as an audio notification (e.g., anoise or ringer), a haptic notification (e.g., a vibration), or a visualnotification (e.g., a light blink) provided by the first device, thecompanion device, or both.

At operation 920, the messaging system 130 detects authorization of thesecond image capture. As with the second image capture, depending on theembodiment, the detecting of authorization may include eitherdetermining that the specified amount of time expired without the firstuser providing input to indicate that the second image capture is to beprevented or receiving input indicative of the first user permitting thefirst image capture.

As shown in FIG. 10, the method 700 may, in some embodiments, includeoperations 1005 and 1010. Although FIG. 10 illustrates the operations1005 and 1010 as being performed prior to operation 730, it shall beappreciated that the operations 1005 and 1010 may be performed at anypoint during the camera sharing session after the second user hasjoined.

At operation 1005, the messaging system 130 receives a view changerequest from the second device. The camera view change request mayinclude a request to rotate or otherwise change the field of view of thecamera. An amount of rotation (e.g., specified in degrees) may beincluded in the view change request. The camera view change request maybe submitted by the second user via a GUI provided by the second device.The GUI may, for example, include a joystick-based control mechanismthat allows the second user to specify specific view changes (e.g., theamount of rotation).

At operation 1010, the messaging system 130 causes a change to the fieldof view of the camera in accordance with the view change request. Themessaging system 130 may cause the change by providing the second devicewith one or more camera commands. For example, the messaging system 130may provide a command to the second device to cause the camera to rotateby an amount specified in the view change request. In this manner, thesecond user may control the camera's view without having to ask thefirst user to move the camera.

As shown in FIG. 11, the method 700 may, in some embodiments, includeoperations 1105, 1110, 1115, 1120, 1125, and 1130. At operation 1105,the messaging system 130 pauses the camera sharing session. Themessaging system 130 may, for example, pause the camera sharing sessionin response to user input indicative of a request to pause the camerasharing (e.g., a press of a button mounted on the glasses 231).

At operation 1110, the messaging system 130 receives a second triggerrequest from the second device while the camera sharing session ispaused. Based on the camera sharing session being paused, the messagingsystem 130 adds the second trigger request to a request queue, atoperation 1115. The request queue may include one or more triggerrequests to be executed once the camera sharing session resumes.

At operation 1120, the messaging system 130 resumes the camera sharingsession. The messaging system 130 may resume the camera sharing inresponse to receiving user input indicative of a request to resume thecamera sharing session.

At operation 1125, the messaging system 130 triggers a third imagecapture at the camera based on the request queue and in response to thecamera sharing session resuming. More specifically, the messaging system130 triggers the third image capture at the camera based on the thirdtrigger request included in the request queue. In general, upon resumingthe camera sharing session, the messaging system 130 clears the requestqueue by executing any trigger requests included therein. The triggeringof the third image capture at the camera results in generation of thirdimage data (e.g., comprising at least a third image).

At operation 1130, the messaging system 130 transmits a third message tothe second device. The third message comprises at least the third imagedata. As with other messages discussed above, the third image data maybe augmented based on user input with additional content such as text,emojis, graphics, and other visual effects.

Although the method 700 is described above as enabling only a seconduser to control image capturing at the camera 160 of the first user, itshall be appreciated that the second user may be one of a plurality ofusers that are enabled to control image capturing at the camera 160 ofthe first users.

Software Architecture

FIG. 12 is a block diagram illustrating an example software architecture1206, which may be used in conjunction with various hardwarearchitectures herein described. FIG. 12 is a non-limiting example of asoftware architecture, and it will be appreciated that many otherarchitectures may be implemented to facilitate the functionalitydescribed herein. The software architecture 1206 may execute on hardwaresuch as a machine 1200 of FIG. 12 that includes, among other things,processors 1204, memory/storage 1206, and I/O components 1218. Arepresentative hardware layer 1252 is illustrated and can represent, forexample, the machine 1200 of FIG. 12. The representative hardware layer1252 includes a processing unit 1254 having associated executableinstructions 1204. The executable instructions 1204 represent theexecutable instructions of the software architecture 1206, includingimplementation of the methods, components, and so forth describedherein. The hardware layer 1252 also includes memory and/or storagemodules 1256, which also have the executable instructions 1204. Thehardware layer 1252 may also comprise other hardware 1258.

In the example architecture of FIG. 12, the software architecture 1206may be conceptualized as a stack of layers where each layer providesparticular functionality. For example, the software architecture 1206may include layers such as an operating system 1202, libraries 1220,frameworks/middleware 1218, applications 1216, and a presentation layer1214. Operationally, the applications 1216 and/or other componentswithin the layers may invoke API calls 1208 through the software stackand receive a response to the API calls 1208 as messages. The layersillustrated are representative in nature and not all softwarearchitectures have all layers. For example, some mobile orspecial-purpose operating systems may not provide aframeworks/middleware 1218, while others may provide such a layer. Othersoftware architectures may include additional or different layers.

The operating system 1202 may manage hardware resources and providecommon services. The operating system 1202 may include, for example, akernel 1222, services 1224, and drivers 1226. The kernel 1222 may act asan abstraction layer between the hardware and the other software layers.For example, the kernel 1222 may be responsible for memory management,processor management (e.g., scheduling), component management,networking, security settings, and so on. The services 1224 may provideother common services for the other software layers. The drivers 1226are responsible for controlling or interfacing with the underlyinghardware. For instance, the drivers 1226 include display drivers, cameradrivers, Bluetooth® drivers, flash memory drivers, serial communicationdrivers (e.g., Universal Serial Bus (USB) drivers), Wi-Fi® drivers,audio drivers, power management drivers, and so forth depending on thehardware configuration.

The libraries 1220 provide a common infrastructure that is used by theapplications 1216 and/or other components and/or layers. The libraries1220 provide functionality that allows other software components toperform tasks in an easier fashion than by interfacing directly with theunderlying operating system 1202 functionality (e.g., kernel 1222,services 1224, and/or drivers 1226). The libraries 1220 may includesystem libraries 1244 (e.g., C standard library) that may providefunctions such as memory allocation functions, string manipulationfunctions, mathematical functions, and the like. In addition, thelibraries 1220 may include API libraries 1246 such as media libraries(e.g., libraries to support presentation and manipulation of variousmedia formats such as MPEG4, H.294, MP3, AAC, AMR, JPG, and PNG),graphics libraries (e.g., an OpenGL framework that may be used to render2D and 3D graphic content on a display), database libraries (e.g.,SQLite that may provide various relational database functions), weblibraries (e.g., WebKit that may provide web browsing functionality),and the like. The libraries 1220 may also include a wide variety ofother libraries 1248 to provide many other APIs to the applications 1216and other software components/modules.

The frameworks/middleware 1218 provide a higher-level commoninfrastructure that may be used by the applications 1216 and/or othersoftware components/modules. For example, the frameworks/middleware 1218may provide various GUI functions, high-level resource management,high-level location services, and so forth. The frameworks/middleware1218 may provide a broad spectrum of other APIs that may be utilized bythe applications 1216 and/or other software components/modules, some ofwhich may be specific to a particular operating system 1202 or platform.

The applications 1216 include built-in applications 1238 and/orthird-party applications 1240. Examples of representative built-inapplications 1238 may include, but are not limited to, a contactsapplication, a browser application, a book reader application, alocation application, a media application, a messaging application,and/or a game application. The third-party applications 1240 may includean application developed using the ANDROID™ or IOS™ software developmentkit (SDK) by an entity other than the vendor of the particular platformand may be mobile software running on a mobile operating system such asIOS™, ANDROID™, WINDOWS® Phone, or other mobile operating systems. Thethird-party applications 1240 may invoke the API calls 1208 provided bythe mobile operating system (such as the operating system 1202) tofacilitate functionality described herein.

The applications 1216 may use built-in operating system functions (e.g.,kernel 1222, services 1224, and/or drivers 1226), libraries 1220, andframeworks/middleware 1218 to create user interfaces to interact withusers of the system. Alternatively, or additionally, in some systemsinteractions with a user may occur through a presentation layer, such asthe presentation layer 1214. In these systems, the application/component“logic” can be separated from the aspects of the application/componentthat interact with a user.

FIG. 13 is a block diagram illustrating components of a machine 1300,according to some example embodiments, able to read instructions from amachine-readable medium (e.g., a machine-readable storage medium) andperform any one or more of the methodologies discussed herein.Specifically, FIG. 13 shows a diagrammatic representation of the machine1200 in the example form of a computer system, within which instructions1310 (e.g., software, a program, an application, an applet, an app, orother executable code) for causing the machine 1300 to perform any oneor more of the methodologies discussed herein may be executed. As such,the instructions 1310 may be used to implement modules or componentsdescribed herein. The instructions 1310 transform the general,non-programmed machine 1300 into a particular machine 1300 programmed tocarry out the described and illustrated functions in the mannerdescribed. In alternative embodiments, the machine 1300 operates as astandalone device or may be coupled (e.g., networked) to other machines.In a networked deployment, the machine 1300 may operate in the capacityof a server machine or a client machine in a server-client networkenvironment, or as a peer machine in a peer-to-peer (or distributed)network environment. The machine 1300 may comprise, but not be limitedto, a server computer, a client computer, a PC, a tablet computer, alaptop computer, a netbook, a set-top box (STB), a PDA, an entertainmentmedia system, a cellular telephone, a smart phone, a mobile device, awearable device (e.g., a smart watch), a smart home device (e.g., asmart appliance), other smart devices, a web appliance, a networkrouter, a network switch, a network bridge, or any machine capable ofexecuting the instructions 1310, sequentially or otherwise, that specifyactions to be taken by the machine 1300. Further, while only a singlemachine 1300 is illustrated, the term “machine” shall also be taken toinclude a collection of machines that individually or jointly executethe instructions 1310 to perform any one or more of the methodologiesdiscussed herein.

The machine 1300 may include processors 1304, memory/storage 1306, andI/O components 1318, which may be configured to communicate with eachother such as via a bus 1302. In an example embodiment, the processors1304 (e.g., a CPU, a reduced instruction set computing (RISC) processor,a complex instruction set computing (CISC) processor, a (GPU, a digitalsignal processor (DSP), an ASIC, a radio-frequency integrated circuit(RFIC), another processor, or any suitable combination thereof) mayinclude, for example, a processor 1308 and a processor 1312 that mayexecute the instructions 1310. Although FIG. 13 shows multipleprocessors, the machine 1300 may include a single processor with asingle core, a single processor with multiple cores (e.g., a multi-coreprocessor), multiple processors with a single core, multiple processorswith multiple cores, or any combination thereof.

The memory/storage 1306 may include a memory 1314, such as a mainmemory, or other memory storage, and a storage unit 1316, bothaccessible to the processors 1304 such as via the bus 1302. The storageunit 1316 and memory 1314 store the instructions 1310 embodying any oneor more of the methodologies or functions described herein. Theinstructions 1310 may also reside, completely or partially, within thememory 1314, within the storage unit 1316, within at least one of theprocessors 1304 (e.g., within the processor's cache memory), or anysuitable combination thereof, during execution thereof by the machine1300. Accordingly, the memory 1314, the storage unit 1316, and thememory of the processors 1304 are examples of machine-readable media.

The I/O components 1318 may include a wide variety of components toreceive input, provide output, produce output, transmit information,exchange information, capture measurements, and so on. The specific I/Ocomponents 1318 that are included in a particular machine 1300 willdepend on the type of machine. For example, portable machines such asmobile phones will likely include a touch input device or other suchinput mechanisms, while a headless server machine will likely notinclude such a touch input device. It will be appreciated that the I/Ocomponents 1318 may include many other components that are not shown inFIG. 13. The I/O components 1318 are grouped according to functionalitymerely for simplifying the following discussion, and the grouping is inno way limiting. In various example embodiments, the I/O components 1318may include output components 1326 and input components 1328. The outputcomponents 1326 may include visual components (e.g., a display such as aplasma display panel (PDP), a light-emitting diode (LED) display, aliquid crystal display (LCD), a projector, or a cathode ray tube (CRT)),acoustic components (e.g., speakers), haptic components (e.g., avibratory motor, resistance mechanisms), other signal generators, and soforth. The input components 1328 may include alphanumeric inputcomponents (e.g., a keyboard, a touch screen display configured toreceive alphanumeric input, a photo-optical keyboard, or otheralphanumeric input components), point-based input components (e.g., amouse, a touchpad, a trackball, a joystick, a motion sensor, or otherpointing instruments), tactile input components (e.g., a physicalbutton, a touch screen display that provides location and/or force oftouches or touch gestures, or other tactile input components), audioinput components (e.g., a microphone), and the like.

In further example embodiments, the I/O components 1318 may includebiometric components 1330, motion components 1334, environmentcomponents 1336, or position components 1338, among a wide array ofother components. For example, the biometric components 1330 may includecomponents to detect expressions (e.g., hand expressions, facialexpressions, vocal expressions, body gestures, or eye tracking), measurebiosignals (e.g., blood pressure, heart rate, body temperature,perspiration, or brain waves), identify a person (e.g., voiceidentification, retinal identification, facial identification,fingerprint identification, or electroencephalogram-basedidentification), and the like. The motion components 1334 may includeacceleration sensor components (e.g., accelerometer), gravitation sensorcomponents, rotation sensor components (e.g., gyroscope), and so forth.The environment components 1336 may include, for example, illuminationsensor components (e.g., photometer), temperature sensor components(e.g., one or more thermometers that detect ambient temperature),humidity sensor components, pressure sensor components (e.g.,barometer), acoustic sensor components (e.g., one or more microphonesthat detect background noise), proximity sensor components (e.g.,infrared sensors that detect nearby objects), gas sensors (e.g., gassensors to detect concentrations of hazardous gases for safety or tomeasure pollutants in the atmosphere), or other components that mayprovide indications, measurements, or signals corresponding to asurrounding physical environment. The position components 1338 mayinclude location sensor components (e.g., a Global Positioning System(GPS) receiver component), altitude sensor components (e.g., altimetersor barometers that detect air pressure from which altitude may bederived), orientation sensor components (e.g., magnetometers), and thelike.

Communication may be implemented using a wide variety of technologies.The/O components 1318 may include communication components 1340 operableto couple the machine 1300 to a network 1332 or devices 1320 via acoupling 1324 and a coupling 1322, respectively. For example, thecommunication components 1340 may include a network interface componentor other suitable device to interface with the network 1332. In furtherexamples, the communication components 1340 may include wiredcommunication components, wireless communication components, cellularcommunication components, Near Field Communication (NFC) components,Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components,and other communication components to provide communication via othermodalities. The devices 1320 may be another machine or any of a widevariety of peripheral devices (e.g., a peripheral device coupled via aUSB).

Moreover, the communication components 1340 may detect identifiers orinclude components operable to detect identifiers. For example, thecommunication components 1340 may include Radio Frequency Identification(RFID) tag reader components, NFC smart tag detection components,optical reader components (e.g., an optical sensor to detectone-dimensional bar codes such as Universal Product Code (UPC) bar code,multi-dimensional bar codes such as Quick Response (QR) code, Azteccode, Data Matrix, Dataglyph, MaxiCode, PDF4114, Ultra Code, UCC RSS-2Dbar code, and other optical codes), or acoustic detection components(e.g., microphones to identify tagged audio signals). In addition, avariety of information may be derived via the communication components1340, such as location via Internet Protocol (IP) geolocation, locationvia Wi-Fi® signal triangulation, location via detecting an NFC beaconsignal that may indicate a particular location, and so forth.

Glossary

“CARRIER SIGNAL” in this context refers to any intangible medium that iscapable of storing, encoding, or carrying instructions for execution bya machine, and includes digital or analog communications signals orother intangible media to facilitate communication of such instructions.Instructions may be transmitted or received over a network using atransmission medium via a network interface device and using any one ofa number of well-known transfer protocols.

“CLIENT DEVICE” in this context refers to any machine that interfaces toa communications network to obtain resources from one or more serversystems or other client devices. A client device may be, but is notlimited to, a mobile phone, desktop computer, laptop, PDA, smart phone,tablet, ultra book, netbook, laptop, multi-processor system,microprocessor-based or programmable consumer electronics system, gameconsole, set-top box, or any other communication device that a user mayuse to access a network.

“COMMUNICATIONS NETWORK” in this context refers to one or more portionsof a network that may be an ad hoc network, an intranet, an extranet, avirtual private network (VPN), a local area network (LAN), a wirelessLAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), ametropolitan area network (MAN), the Internet, a portion of theInternet, a portion of the Public Switched Telephone Network (PSTN), aplain old telephone service (POTS) network, a cellular telephonenetwork, a wireless network, a Wi-Fi® network, another type of network,or a combination of two or more such networks. For example, a network ora portion of a network may include a wireless or cellular network, andthe coupling to the network may be a Code Division Multiple Access(CDMA) connection, a Global System for Mobile communications (GSM)connection, or another type of cellular or wireless coupling. In thisexample, the coupling may implement any of a variety of types of datatransfer technology, such as Single Carrier Radio TransmissionTechnology (1×RTT), Evolution-Data Optimized (EVDO) technology, GeneralPacket Radio Service (GPRS) technology, Enhanced Data rates for GSMEvolution (EDGE) technology, third Generation Partnership Project (3GPP)including 3G, fourth generation wireless (4G) networks, Universal MobileTelecommunications System (UMTS), High-Speed Packet Access (HSPA),Worldwide Interoperability for Microwave Access (WiMAX), Long-TermEvolution (LTE) standard, others defined by various standard-settingorganizations, other long-range protocols, or other data transfertechnology.

“MACHINE-READABLE MEDIUM” in this context refers to a component, device,or other tangible medium able to store instructions and data temporarilyor permanently, and may include, but is not limited to, random-accessmemory (RAM), read-only memory (ROM), buffer memory, flash memory,optical media, magnetic media, cache memory, other types of storage(e.g., Erasable Programmable Read-Only Memory (EPROM)), and/or anysuitable combination thereof. The term “machine-readable medium” shouldbe taken to include a single medium or multiple media (e.g., acentralized or distributed database, or associated caches and servers)able to store instructions. The term “machine-readable medium” shallalso be taken to include any medium, or combination of multiple media,that is capable of storing instructions (e.g., code) for execution by amachine, such that the instructions, when executed by one or moreprocessors of the machine, cause the machine to perform any one or moreof the methodologies described herein. Accordingly, a “machine-readablemedium” refers to a single storage apparatus or device, as well as“cloud-based” storage systems or storage networks that include multiplestorage apparatus or devices. The term “machine-readable medium”excludes signals per se.

“COMPONENT” in this context refers to a device, a physical entity, orlogic having boundaries defined by function or subroutine calls, branchpoints, APIs, or other technologies that provide for the partitioning ormodularization of particular processing or control functions. Componentsmay be combined via their interfaces with other components to carry outa machine process. A component may be a packaged functional hardwareunit designed for use with other components and a part of a program thatusually performs a particular function of related functions. Componentsmay constitute either software components (e.g., code embodied on amachine-readable medium) or hardware components.

A “HARDWARE COMPONENT” is a tangible unit capable of performing certainoperations and may be configured or arranged in a certain physicalmanner. In various example embodiments, one or more computer systems(e.g., a standalone computer system, a client computer system, or aserver computer system) or one or more hardware components of a computersystem (e.g., a processor or a group of processors) may be configured bysoftware (e.g., an application or application portion) as a hardwarecomponent that operates to perform certain operations as describedherein. A hardware component may also be implemented mechanically,electronically, or any suitable combination thereof. For example, ahardware component may include dedicated circuitry or logic that ispermanently configured to perform certain operations. A hardwarecomponent may be a special-purpose processor, such as afield-programmable gate array (FPGA) or an ASIC. A hardware componentmay also include programmable logic or circuitry that is temporarilyconfigured by software to perform certain operations. For example, ahardware component may include software executed by a general-purposeprocessor or other programmable processor.

Once configured by such software, hardware components become specificmachines (or specific components of a machine) uniquely tailored toperform the configured functions and are no longer general-purposeprocessors. It will be appreciated that the decision to implement ahardware component mechanically, in dedicated and permanently configuredcircuitry, or in temporarily configured circuitry (e.g., configured bysoftware) may be driven by cost and time considerations. Accordingly,the phrase “hardware component” (or “hardware-implemented component”)should be understood to encompass a tangible entity, be that an entitythat is physically constructed, permanently configured (e.g.,hardwired), or temporarily configured (e.g., programmed) to operate in acertain manner or to perform certain operations described herein.

Considering embodiments in which hardware components are temporarilyconfigured (e.g., programmed), each of the hardware components need notbe configured or instantiated at any one instance in time. For example,where a hardware component comprises a general-purpose processorconfigured by software to become a special-purpose processor, thegeneral-purpose processor may be configured as respectively differentspecial-purpose processors (e.g., comprising different hardwarecomponents) at different times. Software accordingly configures aparticular processor or processors, for example, to constitute aparticular hardware component at one instance of time and to constitutea different hardware component at a different instance of time.

Hardware components can provide information to, and receive informationfrom, other hardware components. Accordingly, the described hardwarecomponents may be regarded as being communicatively coupled. Wheremultiple hardware components exist contemporaneously, communications maybe achieved through signal transmission (e.g., over appropriate circuitsand buses) between or among two or more of the hardware components. Inembodiments in which multiple hardware components are configured orinstantiated at different times, communications between such hardwarecomponents may be achieved, for example, through the storage andretrieval of information in memory structures to which the multiplehardware components have access. For example, one hardware component mayperform an operation and store the output of that operation in a memorydevice to which it is communicatively coupled. A further hardwarecomponent may then, at a later time, access the memory device toretrieve and process the stored output. Hardware components may alsoinitiate communications with input or output devices, and can operate ona resource (e.g., a collection of information).

The various operations of example methods described herein may beperformed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implementedcomponents that operate to perform one or more operations or functionsdescribed herein. As used herein, “processor-implemented component”refers to a hardware component implemented using one or more processors.Similarly, the methods described herein may be at least partiallyprocessor-implemented, with a particular processor or processors beingan example of hardware. For example, at least some of the operations ofa method may be performed by one or more processors orprocessor-implemented components.

Moreover, the one or more processors may also operate to supportperformance of the relevant operations in a “cloud computing”environment or as a “software as a service” (SaaS). For example, atleast some of the operations may be performed by a group of computers(as examples of machines including processors), with these operationsbeing accessible via a network (e.g., the Internet) and via one or moreappropriate interfaces (e.g., an application programming interface(API)). The performance of certain of the operations may be distributedamong the processors, not only residing within a single machine, butdeployed across a number of machines. In some example embodiments, theprocessors or processor-implemented components may be located in asingle geographic location (e.g., within a home environment, an officeenvironment, or a server farm). In other example embodiments, theprocessors or processor-implemented components may be distributed acrossa number of geographic locations.

“PROCESSOR” in this context refers to any circuit or virtual circuit (aphysical circuit emulated by logic executing on an actual processor)that manipulates data values according to control signals (e.g.,“commands,” “op codes,” “machine code,” etc.) and which producescorresponding output signals that are applied to operate a machine. Aprocessor may, for example, be a CPU, a RISC processor, a CISCprocessor, a GPU, a DSP, an ASIC, a RFIC, or any combination thereof. Aprocessor may further be a multi-core processor having two or moreindependent processors (sometimes referred to as “cores”) that mayexecute instructions contemporaneously.

“TIMESTAMP” in this context refers to a sequence of characters orencoded information identifying when a certain event occurred, (forexample, giving date and time of day) sometimes accurate to a smallfraction of a second.

What is claimed is:
 1. A method comprising: initiating a camera sharingsession based on session configuration information, the sessionconfiguration information comprising a user-generated textualdescription and a user identifier corresponding to a first userpermitted to control, during the camera sharing session, image capturingat a camera embedded in a wearable device worn by a second user, thewearable device being communicatively coupled to a first device, theinitiating of the camera sharing session comprising transmitting, to asecond device associated with the first user, an invitation to join thecamera sharing session, the invitation comprising the user-generatedtextual description, the camera being separate from the second device;receiving, from the second device, a trigger request; based on receivingthe trigger request, triggering an image capture at the camera, theimage capture resulting in first image data comprising a first image;and transmitting, to the second device, a message comprising the firstimage data.
 2. The method of claim 1, further comprising: prior toreceiving the trigger request and based on an indication of the firstuser joining the camera sharing session, triggering a second imagecapture at the camera, the second image capture resulting in secondimage data comprising a second image; transmitting, to the seconddevice, a second message comprising the second image data.
 3. The methodof claim 1, further comprising: receiving, from the first device, inputvia a user interface provided to the first device, the inputcorresponding to the session configuration information.
 4. The method ofclaim 1; wherein the initiating of the camera sharing session furthercomprises: activating the camera, the camera to generate one or moreimages upon being activated; and capturing, in response to first userinput, second image data comprising a second image captured by thecamera; wherein the invitation comprises the second image data.
 5. Themethod of claim 1, further comprising: capturing, in response to seconduser input, second image data comprising a second image at the camera;and providing access to the second image data to the second device. 6.The method of claim 1, further comprising: prior to triggering the imagecapture, providing a notification of the image capture to the firstdevice.
 7. The method of claim 6, wherein: the notification includes arequest for authorization of the image capture; and the method furthercomprises: detecting authorization of the image capture by the firstdevice, wherein the triggering of the image capture is in response todetecting the authorization.
 8. The method of claim 1, wherein: thetrigger request is a first trigger request; the method furthercomprises: receiving, from the second device, a second trigger requestwhile the camera sharing session is paused; and based on the camerasharing session being paused, adding the second trigger request to arequest queue.
 9. The method of claim 8, further comprising: uponresuming the camera sharing session, triggering a second image captureat the camera based on the request queue, the second image captureresulting in second image data; and transmitting, to the second device,a second message comprising the second image data.
 10. A systemcomprising: one or more processors of a server machine; and acomputer-readable memory coupled to the one or more processors andstoring instructions that, when executed by the one or more processors,cause the server machine to perform operations comprising: initiating acamera sharing session based on session configuration information, thesession configuration information comprising a user-generated textualdescription and a user identifier corresponding to a first userpermitted to control, during the camera sharing session, image capturingat a camera embedded in a wearable device worn by a second user, thewearable device being communicatively coupled to a first device; theinitiating of the camera sharing session comprising transmitting, to asecond device associated with the user, an invitation to join the camerasharing session, the invitation comprising the user-generated textualdescription, the camera being separate from the second device;receiving, from the second device; a trigger request; based on receivingthe trigger request, triggering an image capture at the camera, theimage capture resulting in first image data comprising a first image;and transmitting, to the second device, a message comprising the firstimage data.
 11. The system of claim 10, wherein the initiating of thecamera sharing session further comprises: activating the camera, thecamera to generate one or more images upon being activated; andcapturing, in response to first user input by the second user of thefirst device, a second image captured by the camera; transmitting, tothe second device associated with the first user, an invitation to jointhe camera sharing session, the invitation comprises second image. 12.The system of claim 10, further comprising: prior to triggering theimage capture, providing a notification of the image capture to thefirst device, the notification including a request for authorization ofthe image capture; and detecting authorization of the image capture fromthe first device, wherein the triggering of the image capture is inresponse to receiving the authorization.
 13. The system of claim 10,wherein: the trigger request is a first trigger request; the operationsfurther comprise: receiving, from the second device, a second triggerrequest while the camera sharing session is paused; and based on thecamera sharing session being paused, adding the second trigger requestto a request queue.
 14. The system of claim 13, wherein the operationsfurther comprise: upon resuming the camera sharing session, triggering asecond image capture at the camera based on the request queue, thesecond image capture resulting in second image data comprising at leasta second image; and transmitting, to the second device, a second messagecomprising the second image data.
 15. The system of claim 10, whereinthe operations further comprise: in response to receiving user input,generating a second message comprising a second image captured by thecamera; and transmitting, to the second device, the second messagecomprising the second image.
 16. A non-transitory computer-readablemedium storing instructions that, when executed by a computer system,cause the computer system to perform operations comprising: initiating acamera sharing session based on session configuration information, thesession configuration information comprising a user-generated textualdescription and a user identifier corresponding to a first userpermitted to control, during the camera sharing session, image capturingat a camera embedded in a wearable device worn by a second user, thewearable device being communicatively coupled to a first device, theinitiating of the camera sharing session comprising transmitting, to asecond device associated with the user, an invitation to join the camerasharing session, the invitation comprising the user-generated textualdescription, the camera being separate from the second device;receiving, from the second device, a trigger request; based on receivingthe trigger request, triggering an image capture at the camera, theimage capture resulting in first image data comprising a first image;and transmitting, to the second device, a message comprising the firstimage data.